Skip to content

feat(skill-memory): per-skill cross-session recall + historian auto-extraction#181

Open
iceteaSA wants to merge 11 commits into
cortexkit:masterfrom
iceteaSA:skill-memory-pr
Open

feat(skill-memory): per-skill cross-session recall + historian auto-extraction#181
iceteaSA wants to merge 11 commits into
cortexkit:masterfrom
iceteaSA:skill-memory-pr

Conversation

@iceteaSA

@iceteaSA iceteaSA commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds skill-memory — per-skill "motor memory" that gives a skill cross-session recall of its own hard-won lessons (gotchas, discoveries, fixes, workflow steps). When a skill's SKILL.md declares skill-memory: { enabled: true }, accumulated notes for that skill surface automatically in a <skill-memory> block appended to the skill tool's result on every load — and, with the historian extension, the historian writes those notes automatically during compaction (no agent action required).

It's fully opt-in per skill and cache-safe by construction: the block rides the tool-result tail (conversation), never the cached system/m[0] prefix, so it can't bust the prompt cache.

How it works

  • Transparent recall — three-hook augmentation: tool.definition advertises an intent param; tool.execute.before stashes the intent (bounded TTL); the after-hook parses the skill's Base directory, reads its SKILL.md frontmatter, and formats the recall block. Lands in the tool RESULT (cache-safe).
  • Write pathsctx_skill_note (agent-authored) and the historian (auto-extracted). Both dedup on a normalized hash.
  • Intent-scoped ranking — a recall cascade: model-matched embeddings → cosine blend over intent_embedding + delta_embedding (relevance/recency/hit weights tunable per skill via ranking_* frontmatter); FTS5 fallback over a content-linked skill_memory_fts vtable; flat recency×hit fallback.
  • Historian auto-extraction — the historian sees TC: skill(<name>) markers in its chunk and emits a <skill_observations> block; both the OpenCode and Pi runners promote those post-commit as global notes (project_identity='*', source_type='historian'), recallable from any project.

Review units (4 commits)

The branch is organized into four coherent, reviewable phases:

  1. P1 — transparent per-skill recall: skill_memory table migration, the three-hook augmentation, flat recall + storage, ctx_skill_note/ctx_skill_recall tools, opt-in distill-skill-memory dreamer task, TUI/ctx-status stats, docs.
  2. P2 — embeddings + intent-scoped recall: delta_embedding + recall_count columns + skill_memory_fts FTS5 vtable; embed-on-write; the cosine/FTS recall cascade; a programmatic (no-LLM) reembed pre-step.
  3. P3a — historian-extraction foundation: the TC: skill(<name>) marker keystone; origin_project + source_type columns; global-tier notes unified under project_identity='*' (collision-merge); partitionKey routing.
  4. P3b — historian auto-extraction pipeline: prompt emits <skill_observations>, parser, validated-result threading, both runners promote via the shared promoteSkillObservations helper, plus an initializeDatabase self-heal net (re-creates skill_memory + ensureColumn so an upgraded DB recovers even if a migration row is lost).

Schema / migrations

Three migrations (numbered after the current master ceiling): skill_memory table, then delta_embedding/recall_count/FTS, then origin_project/source_type/* unification. LATEST_SUPPORTED_VERSION bumped in lockstep (the schema-version-fence test enforces it). Migration bodies are ensureColumn/IF NOT EXISTS idempotent.

Testing

Full plugin + Pi suites pass (one unrelated pre-existing full-suite ordering flake in tui-config.test.ts that passes in isolation), tsc clean both packages, lint clean, build produces all bundles. Dedicated coverage for the migrations (coexistence + fence), recall rungs, the tools, FTS triggers/backfill, the '*' collision-merge, and the historian promotion path on both runners. Verified working live: the historian auto-extraction writes genuine source_type='historian' notes, embeddings populate, and the read-side recall_count increments on surfacing.

Notes for reviewers

  • Migration version numbers are placeholders relative to this fork's base — happy to renumber to whatever slots are free at merge time.
  • The four commits are independently meaningful; if you'd prefer this as stacked PRs (P1 / P2 / historian), I can split it.

View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.


Summary by cubic

Adds per-skill cross-session memory: a cache-safe <skill-memory> block is appended to each skill tool RESULT with intent-scoped recall (embeddings + FTS) and historian auto-extraction into global notes. Ships the opt-in distill-skill-memory dreamer task, ctx_skill_note/ctx_skill_recall tools, TUI/CLI stats, and DB migrations to v52 with a self-heal path.

  • New Features

    • Transparent per-skill recall: the skill tool optionally accepts intent; before-hook stashes it and after-hook injects recall; ctx_skill_note writes and ctx_skill_recall reads; Status/TUI show per-project totals and pinned counts.
    • Ranking + embeddings: cosine blend over intent_embedding + delta_embedding with FTS5 fallback; programmatic re-embed backfills NULL/stale vectors before distill-skill-memory.
    • Historian auto-extraction: TC: skill(<name>) markers → <skill_observations>; both runners promote via promoteSkillObservations as global '*' notes (source_type='historian').
    • Schema/migrations/self-heal: skill_memory table + FTS vtable/columns; LATEST_SUPPORTED_VERSION=52; initializeDatabase re-creates missing objects and rebuilds skill_memory_fts when needed; dashboard/CLI/config include the distill-skill-memory task (off by default).
  • Bug Fixes

    • Cross-partition recall: union a skill’s partition with global '*' so project-local skills surface historian-written notes; writes/dedup remain exact-partition.
    • Frontmatter gating: reject ctx_skill_note when skill-memory.enabled is false or missing to prevent orphaned, unrecallable notes.
    • Disabled-path safety and routing: guard ctx_skill_note when the plugin is disabled; correctly classify singular ~/.config/opencode/skill/** as global; normalize Windows paths.
    • Frontmatter parsing: accept inline skill-memory: { enabled: true }; anchor to start-of-file; tolerate leading BOM/whitespace; strip inline # from unquoted scalars.
    • Historian marker + intent stash: emit TC: skill(<name>) verbatim (CR/LF/tab only are unsafe); key stashed intents by sessionID:callID and prune on session delete.
    • Prompt guidance + observability: drop ctx_memory cross-reference in skill guidance when memory is off; log recall errors; escape apostrophes in SQL.
    • Token budgeting + tier derivation: count per-note XML framing and clamp pinned budget; derive tier via dirname(resolvedPath) for robustness.

Written for commit 3a1733d. Summary will update on new commits.

Review in cubic

Greptile Summary

Adds skill-memory — an opt-in, cache-safe per-skill cross-session recall system. When a skill's SKILL.md declares skill-memory: { enabled: true }, the after-hook appends a <skill-memory> block to the skill tool result on every load; the historian auto-extraction pipeline promotes <skill_observations> from compaction runs as global '*' notes surfaced across all projects via a union predicate.

  • Three new SQLite migrations (v50–v52) add the skill_memory table, FTS5 vtable with content-linked triggers, delta_embedding/recall_count columns, and origin_project/source_type historian columns; the initializeDatabase self-heal re-creates all objects with IF NOT EXISTS + ensureColumn guards and conditionally rebuilds the FTS index when empty but rows exist.
  • Recall runs a four-rung cascade: cosine blend over intent_embedding+delta_embedding → FTS5 MATCH fallback → flat recency×hit; results are partition-unioned so a project-local skill surfaces historian-written global '*' notes while write/dedup paths remain exact-partition.
  • All bugs flagged in the previous review round (intentByCallId cross-session eviction, redundant dynamic import, missing FTS rebuild in self-heal, project-local historian notes orphaned, ctx_skill_note writing to disabled skills) are confirmed fixed in the current diff.

Confidence Score: 5/5

Safe to merge. All issues from the previous review are fixed; the remaining observations are minor naming/redundancy nits with no impact on correctness.

The three-hook recall injection, historian promotion, and migration self-heal are all correctly implemented. Previously reported bugs — cross-session intent eviction, orphaned project-local historian notes, ctx_skill_note writing to disabled skills, missing FTS rebuild in initializeDatabase — are all confirmed resolved. The two remaining observations (double recallPartitionPredicate call in searchSkillMemoryFts and the pre-partitioned key convention in the recall stack) are style/maintenance concerns with no effect on runtime behavior.

The storage.ts and recall.ts skill-memory files have minor code-quality observations but no correctness issues. The migration files and storage-db.ts self-heal are solid.

Important Files Changed

Filename Overview
packages/plugin/src/features/magic-context/skill-memory/storage.ts New skill_memory storage layer with correct recall-partition predicate, dedup, FTS integration, and stats queries; minor issue with double recallPartitionPredicate call in searchSkillMemoryFts.
packages/plugin/src/features/magic-context/skill-memory/recall.ts Four-rung recall cascade (cosine → FTS → flat) with budgetFill and pinned-first ordering; the projectIdentity parameter throughout the stack silently receives a pre-partitioned key, which works due to partitionKey idempotency but is a latent naming hazard.
packages/plugin/src/features/magic-context/migrations.ts Three new migrations (v50/v51/v52) add skill_memory table, FTS vtable+triggers, delta_embedding/recall_count columns, and origin_project/source_type + '*' unification; collision-merge and interrupted-rerun logic is sound.
packages/plugin/src/features/magic-context/storage-db.ts Self-heal path in initializeDatabase creates skill_memory with all columns (including v51/v52 additions), adds ensureColumn guards for existing DBs, and correctly conditionally rebuilds the FTS index when empty but rows exist.
packages/plugin/src/tools/ctx-skill-note/tools.ts Correctly guards on frontmatterConfig?.enabled before inserting (matching the fix for the previously reported orphan-write issue), performs exact-hash and cosine-similarity dedup, and handles concurrent-insert race via UNIQUE constraint catch.
packages/plugin/src/features/magic-context/skill-memory/promote.ts Historian promotion correctly writes tier='global'/project_identity='*' rows with per-item best-effort error handling; uses obs.lesson as both intent and delta (intentional — historian has no separate intent context).
packages/plugin/src/hooks/magic-context/hook-handlers.ts Three-hook augmentation (definition/before/after) correctly uses hoisted single await import(…provenance) shared between registry-populate and injection blocks; intent stash correctly keyed sessionID:callID after the dd8202b fix.
packages/plugin/src/hooks/magic-context/hook.ts onSessionDeleted now correctly prunes intentByCallId via prefix on sessionID:callID composite key, fixing the cross-session eviction bug reported in the previous round.
packages/plugin/src/features/magic-context/skill-memory/frontmatter.ts Minimal YAML parser handles inline flow-mapping, block form, inline comments, BOM/leading whitespace, and is start-anchored; all advertised edge cases in the PR description are covered.
packages/plugin/src/hooks/magic-context/skill-tool-definition.ts Correctly assigns output.jsonSchema (rather than mutating Effect schema parameters) to expose the optional intent field to the model; forward-compatible by extending an existing jsonSchema in place rather than overwriting it.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Model
    participant SkillTool as skill tool (hook)
    participant HookHandlers
    participant Registry as skillLoadRegistry
    participant IntentStash as intentByCallId
    participant RecallCore as recallSkillMemoryBlock
    participant DB as SQLite (skill_memory)
    participant Historian

    Model->>SkillTool: skill(name, intent?)
    SkillTool->>IntentStash: stash intent keyed sessionID:callID
    SkillTool->>Model: skill output (Base directory line)
    HookHandlers->>HookHandlers: parse provenance from output
    HookHandlers->>HookHandlers: readFileSync SKILL.md → parseFrontmatterConfig
    HookHandlers->>Registry: "set sessionID:skillId → {tier, path, frontmatterConfig}"
    HookHandlers->>IntentStash: getAndDelete intent by sessionID:callID
    HookHandlers->>RecallCore: recallSkillMemoryBlock(skill, intent, scope, projectIdentity)
    RecallCore->>DB: embedTextForProject(intent) → vector
    alt embeddings available (rung 1)
        RecallCore->>DB: getRankingCandidates → cosine rank
    else FTS fallback (rung 3)
        RecallCore->>DB: searchSkillMemoryFts(sanitizedIntent)
    else flat fallback (rung 2/4)
        RecallCore->>DB: getSkillMemoryNotes ORDER BY recency x hit
    end
    RecallCore->>DB: bumpRecallCountByIds
    RecallCore->>HookHandlers: skill-memory XML block
    HookHandlers->>Model: append block to tool result

    Model->>DB: ctx_skill_note(skill, intent, kind, delta)
    DB->>DB: hash-dedup + cosine-dedup + insertSkillMemoryNote

    Historian->>DB: promoteSkillObservations(observations[])
    DB->>DB: "tier=global, project_identity=*, source_type=historian"
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Model
    participant SkillTool as skill tool (hook)
    participant HookHandlers
    participant Registry as skillLoadRegistry
    participant IntentStash as intentByCallId
    participant RecallCore as recallSkillMemoryBlock
    participant DB as SQLite (skill_memory)
    participant Historian

    Model->>SkillTool: skill(name, intent?)
    SkillTool->>IntentStash: stash intent keyed sessionID:callID
    SkillTool->>Model: skill output (Base directory line)
    HookHandlers->>HookHandlers: parse provenance from output
    HookHandlers->>HookHandlers: readFileSync SKILL.md → parseFrontmatterConfig
    HookHandlers->>Registry: "set sessionID:skillId → {tier, path, frontmatterConfig}"
    HookHandlers->>IntentStash: getAndDelete intent by sessionID:callID
    HookHandlers->>RecallCore: recallSkillMemoryBlock(skill, intent, scope, projectIdentity)
    RecallCore->>DB: embedTextForProject(intent) → vector
    alt embeddings available (rung 1)
        RecallCore->>DB: getRankingCandidates → cosine rank
    else FTS fallback (rung 3)
        RecallCore->>DB: searchSkillMemoryFts(sanitizedIntent)
    else flat fallback (rung 2/4)
        RecallCore->>DB: getSkillMemoryNotes ORDER BY recency x hit
    end
    RecallCore->>DB: bumpRecallCountByIds
    RecallCore->>HookHandlers: skill-memory XML block
    HookHandlers->>Model: append block to tool result

    Model->>DB: ctx_skill_note(skill, intent, kind, delta)
    DB->>DB: hash-dedup + cosine-dedup + insertSkillMemoryNote

    Historian->>DB: promoteSkillObservations(observations[])
    DB->>DB: "tier=global, project_identity=*, source_type=historian"
Loading

Comments Outside Diff (1)

  1. packages/plugin/src/features/magic-context/skill-memory/recall.ts, line 481-484 (link)

    P2 Bare catch {} makes recall errors invisible

    Any exception thrown inside recallSkillMemoryBlock — a SQLite error, embedding provider crash, or a coding mistake — is silently swallowed and returns an empty string. From the caller's perspective this is indistinguishable from "no notes exist" or "skill-memory disabled". At minimum a sessionLog or console.warn call here would let a developer diagnose why the recall block is absent without attaching a debugger.

Reviews (8): Last reviewed commit: "fix(skill-memory): reject ctx_skill_note..." | Re-trigger Greptile

@iceteaSA iceteaSA force-pushed the skill-memory-pr branch 4 times, most recently from dc83db6 to 4034019 Compare June 25, 2026 11:37
@iceteaSA iceteaSA marked this pull request as ready for review June 25, 2026 13:18

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

11 issues found across 78 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/plugin/src/features/magic-context/dreamer/task-executor.ts">

<violation number="1" location="packages/plugin/src/features/magic-context/dreamer/task-executor.ts:419">
P2: Re-embed pre-step errors are suppressed, allowing successful task completion reporting despite a failed prerequisite data maintenance step.</violation>
</file>

Note: This PR contains a large number of files. cubic only reviews up to 40 files per PR, so some files may not have been reviewed. cubic prioritizes the most important files to review.
On a pro plan you can use ultrareview for larger PRs.

Re-trigger cubic

Comment thread CONFIGURATION.md Outdated
Comment thread packages/plugin/src/features/magic-context/skill-memory/promote.ts Outdated
Comment thread packages/plugin/src/index.ts Outdated
Comment thread packages/plugin/src/tools/ctx-skill-recall/types.ts
// Skill-memory P2: re-embed stale/NULL skill-note vectors BEFORE the
// distill agentic pass so the prompt sees a fully-embedded corpus and
// P1-era notes promote from the FTS rung to the cosine rung.
if (config.task === "distill-skill-memory") {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Re-embed pre-step errors are suppressed, allowing successful task completion reporting despite a failed prerequisite data maintenance step.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/plugin/src/features/magic-context/dreamer/task-executor.ts, line 419:

<comment>Re-embed pre-step errors are suppressed, allowing successful task completion reporting despite a failed prerequisite data maintenance step.</comment>

<file context>
@@ -412,7 +413,18 @@ export function createDreamTaskExecutor(deps: DreamTaskExecutorDeps): TaskExecut
+            // Skill-memory P2: re-embed stale/NULL skill-note vectors BEFORE the
+            // distill agentic pass so the prompt sees a fully-embedded corpus and
+            // P1-era notes promote from the FTS rung to the cosine rung.
+            if (config.task === "distill-skill-memory") {
+                try {
+                    await reembedStaleSkillNotes(db, projectIdentity);
</file context>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Holding this one as working-as-intended. The catch is not silent — it logs [dreamer] distill-skill-memory reembed pre-step failed: ${e} (task-executor.ts, the line directly inside the catch). The suppression is deliberate: re-embedding is a best-effort optimization pre-step, not a prerequisite — if it fails, the affected notes simply stay on the FTS recall rung instead of the cosine rung, and the distill report still runs correctly. Letting a reembed failure fail the whole task would block a report that doesn't depend on it. The failure is observable via the log; happy to escalate to a metric/warning if you'd prefer louder signal.

Comment thread packages/plugin/src/hooks/magic-context/read-session-formatting.ts Outdated
Comment thread packages/plugin/src/hooks/magic-context/read-session-formatting.ts
Comment thread packages/plugin/src/features/magic-context/skill-memory/frontmatter.ts Outdated
Comment thread packages/plugin/src/features/magic-context/skill-memory/frontmatter.ts Outdated
Comment thread packages/plugin/src/hooks/magic-context/hook.ts Outdated
Comment thread packages/plugin/src/hooks/magic-context/hook-handlers.ts
Comment thread packages/plugin/src/features/magic-context/storage-db.ts

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4 issues found across 15 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/plugin/src/features/magic-context/dreamer/task-executor.ts">

<violation number="1" location="packages/plugin/src/features/magic-context/dreamer/task-executor.ts:419">
P2: Re-embed pre-step errors are suppressed, allowing successful task completion reporting despite a failed prerequisite data maintenance step.</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread packages/plugin/src/features/magic-context/dreamer/task-prompts.ts Outdated
Comment thread packages/plugin/src/features/magic-context/skill-memory/frontmatter.ts Outdated
Comment thread packages/plugin/src/hooks/magic-context/read-session-formatting.ts Outdated
Comment thread packages/plugin/src/features/magic-context/skill-memory/frontmatter.test.ts Outdated
Comment thread packages/plugin/src/features/magic-context/skill-memory/promote.ts
@iceteaSA iceteaSA marked this pull request as draft June 25, 2026 14:55
iceteaSA pushed a commit to iceteaSA/magic-context that referenced this pull request Jun 25, 2026
…routing/parser gaps)

Council review (deepseek/sonnet/gpt-5.5) of PR cortexkit#181:

- Must (consensus rev-2+rev-3): the ctx_skill_note fail-loud guard threw during
  plugin init when the plugin is disabled (enabled:false OR conflict-disabled) —
  createSessionHooks returns {magicContext:null} by design, so the unconditional
  guard crashed the entry module on the disabled path. Gate it on
  pluginConfig.enabled; pass a throwaway Map to createToolRegistry (which
  early-returns {} when disabled and never reads it).
- Must (rev-3): singular ~/.config/opencode/skill/ global path was misclassified
  as project tier (opencode's pattern is {skill,skills}/**/SKILL.md) — fixed in
  deriveSkillTier/deriveSkillSource + the ctx_skill_recall cold-start search list.
- Must (rev-3): the frontmatter parser rejected the inline flow-mapping form
  'skill-memory: { enabled: true }' — the EXACT form the ctx_skill_recall
  remediation message and ARCHITECTURE/CONFIGURATION/README advertise. Added
  inline-mapping parsing so guidance and parser agree.
- Should (consensus rev-1+rev-3): recallSkillMemoryBlock swallowed all errors
  silently — added a log() so FTS/blob corruption is diagnosable (still no-throw).

Regression tests: inline frontmatter form (3 cases), singular skill/ global path
(2 cases).
iceteaSA pushed a commit to iceteaSA/magic-context that referenced this pull request Jun 25, 2026
…routing/parser gaps)

Council review (deepseek/sonnet/gpt-5.5) of PR cortexkit#181:

- Must (consensus rev-2+rev-3): the ctx_skill_note fail-loud guard threw during
  plugin init when the plugin is disabled (enabled:false OR conflict-disabled) —
  createSessionHooks returns {magicContext:null} by design, so the unconditional
  guard crashed the entry module on the disabled path. Gate it on
  pluginConfig.enabled; pass a throwaway Map to createToolRegistry (which
  early-returns {} when disabled and never reads it).
- Must (rev-3): singular ~/.config/opencode/skill/ global path was misclassified
  as project tier (opencode's pattern is {skill,skills}/**/SKILL.md) — fixed in
  deriveSkillTier/deriveSkillSource + the ctx_skill_recall cold-start search list.
- Must (rev-3): the frontmatter parser rejected the inline flow-mapping form
  'skill-memory: { enabled: true }' — the EXACT form the ctx_skill_recall
  remediation message and ARCHITECTURE/CONFIGURATION/README advertise. Added
  inline-mapping parsing so guidance and parser agree.
- Should (consensus rev-1+rev-3): recallSkillMemoryBlock swallowed all errors
  silently — added a log() so FTS/blob corruption is diagnosable (still no-throw).

Regression tests: inline frontmatter form (3 cases), singular skill/ global path
(2 cases).
iceteaSA pushed a commit to iceteaSA/magic-context that referenced this pull request Jun 25, 2026
…routing/parser gaps)

Council review (deepseek/sonnet/gpt-5.5) of PR cortexkit#181:

- Must (consensus rev-2+rev-3): the ctx_skill_note fail-loud guard threw during
  plugin init when the plugin is disabled (enabled:false OR conflict-disabled) —
  createSessionHooks returns {magicContext:null} by design, so the unconditional
  guard crashed the entry module on the disabled path. Gate it on
  pluginConfig.enabled; pass a throwaway Map to createToolRegistry (which
  early-returns {} when disabled and never reads it).
- Must (rev-3): singular ~/.config/opencode/skill/ global path was misclassified
  as project tier (opencode's pattern is {skill,skills}/**/SKILL.md) — fixed in
  deriveSkillTier/deriveSkillSource + the ctx_skill_recall cold-start search list.
- Must (rev-3): the frontmatter parser rejected the inline flow-mapping form
  'skill-memory: { enabled: true }' — the EXACT form the ctx_skill_recall
  remediation message and ARCHITECTURE/CONFIGURATION/README advertise. Added
  inline-mapping parsing so guidance and parser agree.
- Should (consensus rev-1+rev-3): recallSkillMemoryBlock swallowed all errors
  silently — added a log() so FTS/blob corruption is diagnosable (still no-throw).

Regression tests: inline frontmatter form (3 cases), singular skill/ global path
(2 cases).
@iceteaSA iceteaSA marked this pull request as ready for review June 25, 2026 16:09

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4 issues found across 78 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/plugin/src/features/magic-context/dreamer/task-executor.ts">

<violation number="1" location="packages/plugin/src/features/magic-context/dreamer/task-executor.ts:419">
P2: Re-embed pre-step errors are suppressed, allowing successful task completion reporting despite a failed prerequisite data maintenance step.</violation>
</file>

Note: This PR contains a large number of files. cubic only reviews up to 40 files per PR, so some files may not have been reviewed. cubic prioritizes the most important files to review.
On a pro plan you can use ultrareview for larger PRs.

Re-trigger cubic

Comment thread ARCHITECTURE.md Outdated
Comment thread ARCHITECTURE.md
Comment thread packages/plugin/src/hooks/magic-context/read-session-formatting.ts
Comment thread packages/plugin/src/features/magic-context/skill-memory/provenance.ts Outdated
iceteaSA pushed a commit to iceteaSA/magic-context that referenced this pull request Jun 25, 2026
…routing/parser gaps)

Council review (deepseek/sonnet/gpt-5.5) of PR cortexkit#181:

- Must (consensus rev-2+rev-3): the ctx_skill_note fail-loud guard threw during
  plugin init when the plugin is disabled (enabled:false OR conflict-disabled) —
  createSessionHooks returns {magicContext:null} by design, so the unconditional
  guard crashed the entry module on the disabled path. Gate it on
  pluginConfig.enabled; pass a throwaway Map to createToolRegistry (which
  early-returns {} when disabled and never reads it).
- Must (rev-3): singular ~/.config/opencode/skill/ global path was misclassified
  as project tier (opencode's pattern is {skill,skills}/**/SKILL.md) — fixed in
  deriveSkillTier/deriveSkillSource + the ctx_skill_recall cold-start search list.
- Must (rev-3): the frontmatter parser rejected the inline flow-mapping form
  'skill-memory: { enabled: true }' — the EXACT form the ctx_skill_recall
  remediation message and ARCHITECTURE/CONFIGURATION/README advertise. Added
  inline-mapping parsing so guidance and parser agree.
- Should (consensus rev-1+rev-3): recallSkillMemoryBlock swallowed all errors
  silently — added a log() so FTS/blob corruption is diagnosable (still no-throw).

Regression tests: inline frontmatter form (3 cases), singular skill/ global path
(2 cases).
iceteaSA pushed a commit to iceteaSA/magic-context that referenced this pull request Jun 26, 2026
…routing/parser gaps)

Council review (deepseek/sonnet/gpt-5.5) of PR cortexkit#181:

- Must (consensus rev-2+rev-3): the ctx_skill_note fail-loud guard threw during
  plugin init when the plugin is disabled (enabled:false OR conflict-disabled) —
  createSessionHooks returns {magicContext:null} by design, so the unconditional
  guard crashed the entry module on the disabled path. Gate it on
  pluginConfig.enabled; pass a throwaway Map to createToolRegistry (which
  early-returns {} when disabled and never reads it).
- Must (rev-3): singular ~/.config/opencode/skill/ global path was misclassified
  as project tier (opencode's pattern is {skill,skills}/**/SKILL.md) — fixed in
  deriveSkillTier/deriveSkillSource + the ctx_skill_recall cold-start search list.
- Must (rev-3): the frontmatter parser rejected the inline flow-mapping form
  'skill-memory: { enabled: true }' — the EXACT form the ctx_skill_recall
  remediation message and ARCHITECTURE/CONFIGURATION/README advertise. Added
  inline-mapping parsing so guidance and parser agree.
- Should (consensus rev-1+rev-3): recallSkillMemoryBlock swallowed all errors
  silently — added a log() so FTS/blob corruption is diagnosable (still no-throw).

Regression tests: inline frontmatter form (3 cases), singular skill/ global path
(2 cases).
Tehan added 9 commits July 2, 2026 17:19
Per-skill "motor memory": when a skill's SKILL.md declares
`skill-memory: { enabled: true }`, accumulated gotchas/discoveries/fixes/
workflow-steps surface in a <skill-memory> block appended to the skill
tool's RESULT on every load (cache-safe — rides the tool-result tail).
Agents write back via ctx_skill_note; ctx_skill_recall is the explicit
companion to the transparent after-hook.

- migration: skill_memory table (per-skill; tier project/global; UNIQUE on
  skill_id/tier/project_identity/normalized_hash) + lookup indexes.
- three-hook augmentation: tool.definition advertises an `intent` param;
  tool.execute.before stashes intent (bounded TTL); after-hook parses the
  skill's Base directory, reads SKILL.md frontmatter, formats the block.
- flat recency×hit recall + storage layer; ctx_skill_note / ctx_skill_recall.
- opt-in distill-skill-memory dreamer task; agent-prompt guidance; TUI/ctx-status stats.
- docs: ARCHITECTURE / STRUCTURE / CONFIGURATION / README.
Upgrade recall from flat recency×hit to a multi-rung cascade: intent +
model-matched embeddings → cosine blend across intent_embedding +
delta_embedding (relevance/recency/hit weights tunable per skill via
ranking_* frontmatter); intent + no model match → FTS5 fallback over the
content-linked skill_memory_fts vtable; empty → flat fallback.

- migration: delta_embedding + recall_count columns + skill_memory_fts FTS5 vtable.
- embed-on-write in insertSkillMemoryNote; delta-only semantic dedup.
- programmatic, no-LLM reembed pre-step for the distill-skill-memory dreamer task.
- read-side recall_count (distinct from write-side hit_count).
- canonical vector serde + dedup/ranking/FTS query helpers.
…ication (P3a)

Foundation for the historian to auto-capture skill notes cross-project.

- surface the skill name in the historian chunk as a `TC: skill(<name>)`
  marker (the keystone — the tool input name was previously dropped).
- migration: origin_project + source_type columns; unify global-tier notes
  under project_identity='*' (collision-merge) so a global note is one row
  recallable from any repo.
- partitionKey helper routes global write/recall/reembed/stats through '*';
  recall reads global-tier from '*' (cross-project); reembed sweeps '*'.
Close the loop so the historian writes skill notes during compaction
without an agent volunteering ctx_skill_note.

- historian prompt emits a <skill_observations> block; parser extracts it;
  threaded through the validated historian result.
- both runners (OpenCode + Pi) promote skill observations post-commit via
  the shared promoteSkillObservations helper, gated by
  promotionActive && !discardedLast, writing global '*' notes with
  source_type='historian'.
- self-heal net: initializeDatabase re-creates skill_memory + ensureColumn
  so an upgraded DB recovers even if a migration row is lost.
- Remove committed <<<<<<< HEAD conflict marker in CONFIGURATION.md (P1)
- Move injectSkillIntentParam before the lastChatContext guard so the intent
  param is advertised even on tool.definition flights before first chat.message
- Key intentByCallId by sessionID:callID + prefix-prune on session delete so a
  concurrent session's delete can't evict another session's in-flight intents
- Log silent catch in promoteSkillObservations (observability for dropped writes)
- Anchor frontmatter regex to start-of-file (drop m flag) so a later --- rule
  can't be misparsed; strip inline # comments from unquoted YAML scalars + block header
- Scope distill report SQL to ('<identity>','*') instead of non-deterministic LIMIT 1
- Don't truncate skill name in TC: skill(<name>) marker (identity key); sanitize
  newlines/control chars
- Normalize backslash->slash after fileURLToPath for Windows provenance checks
- FTS self-heal rebuild in initializeDatabase when skill_memory_fts is empty but
  skill_memory has rows
- Move ctx_skill_recall _test* DI fields to a separate test-only deps type
- Hoist the shared registryKey dynamic import (one import, both blocks)

Pushback: reembed pre-step errors are already logged (task-executor.ts) — the
non-blocking try/catch is by design (failure leaves notes on the FTS rung).
…2/P3)

- P1: recall now unions the skill's own partition with the global '*' partition
  (recallPartitionPredicate helper) so a PROJECT-LOCAL skill surfaces
  historian-written global notes — previously orphaned (tier='project' query
  never matched tier='global'/'*'). Write/dedup paths stay exact-partition.
- Escape apostrophes in projectPath before SQL string interpolation in the
  distill prompt template.
- Frontmatter regex tolerates a leading UTF-8 BOM / whitespace (still start-anchored).
- TC: skill(<name>) marker emits the name VERBATIM when marker-safe, else drops
  it — never mutates the identity key (recall keys on raw input.name).
- Fix misleading frontmatter test: now actually exercises a '#' inside a quoted
  scalar (preserved) vs unquoted (comment-stripped).

Regression tests: project-local skill recalls a global historian note; agent
project note + historian global note both surface for the same skill.
…routing/parser gaps)

Council review (deepseek/sonnet/gpt-5.5) of PR cortexkit#181:

- Must (consensus rev-2+rev-3): the ctx_skill_note fail-loud guard threw during
  plugin init when the plugin is disabled (enabled:false OR conflict-disabled) —
  createSessionHooks returns {magicContext:null} by design, so the unconditional
  guard crashed the entry module on the disabled path. Gate it on
  pluginConfig.enabled; pass a throwaway Map to createToolRegistry (which
  early-returns {} when disabled and never reads it).
- Must (rev-3): singular ~/.config/opencode/skill/ global path was misclassified
  as project tier (opencode's pattern is {skill,skills}/**/SKILL.md) — fixed in
  deriveSkillTier/deriveSkillSource + the ctx_skill_recall cold-start search list.
- Must (rev-3): the frontmatter parser rejected the inline flow-mapping form
  'skill-memory: { enabled: true }' — the EXACT form the ctx_skill_recall
  remediation message and ARCHITECTURE/CONFIGURATION/README advertise. Added
  inline-mapping parsing so guidance and parser agree.
- Should (consensus rev-1+rev-3): recallSkillMemoryBlock swallowed all errors
  silently — added a log() so FTS/blob corruption is diagnosable (still no-throw).

Regression tests: inline frontmatter form (3 cases), singular skill/ global path
(2 cases).
- budgetFill now counts per-note XML framing (~20 tokens) so the rendered
  <skill-memory> block stays within max_tokens instead of ~13% overshoot (rev-1).
- clamp effective pinned budget to min(max_pinned_tokens, max_tokens) so the
  default 4000>1500 can't imply pinned gets more room than the whole block (rev-2).
- ctx_skill_recall: derive tier via dirname(resolvedPath) instead of a fragile
  .replace('/SKILL.md','') (rev-2).
Updated the budget-truncation test for the framing-inclusive math.
- provenance.ts: anchor the Base-directory regex to line-start (^…/gm) and take
  the LAST match — opencode appends the provenance line at the END of tool
  output, so a skill whose CONTENT echoes 'Base directory for this skill:' (e.g.
  a skill documenting skill-memory) would otherwise shadow the real line and
  misdirect recall to a bogus identity.
- read-session-formatting.ts: narrow the marker-safe exclusion to CR/LF/tab only
  — a ')' does not break the single-line TC: skill(<name>) marker and the
  historian reads it as natural language, so a ')'-containing name is preserved
  verbatim (identity key) instead of dropped.
- ARCHITECTURE.md: update the 'Skill-memory (motor memory)' Key Abstraction to
  the shipped reality (v50/51/52, multi-rung embedding+FTS recall, global-'*'
  union) — was stale (v37, 'P2 TODO'). Remove the PR-added duplicate
  'Tag Identity (v3.3.1+)' section (upstream owns the lean '## Tag identity';
  Tag Identity is unrelated to skill-memory — rebase scope-creep).

Regression tests: provenance last-match + mid-line rejection; ')' name preserved
+ CR/LF/tab still dropped.
…emory off

Rebase-onto-v0.29.0 resolution completion. Upstream ab4f01c added a
memory.enabled gate that drops ALL ctx_memory mentions from the system
prompt when memory is off (ctx_memory is then unregistered). The skill-memory
guidance carried a 'those belong in ctx_memory' cross-reference that violated
the new contract (buildMagicContextSection memory-gating tests). Parameterized
ctxSkillMemoryGuidance(memoryEnabled) so the cross-ref drops when memory is off;
skill-memory itself stays ungated (independent store).
Comment thread packages/plugin/src/tools/ctx-skill-note/tools.ts
…d in frontmatter

Counterpart to ctx_skill_recall's enabled-guard (greptile review, PR cortexkit#181):
without it, notes for skills that never opted in inserted successfully but
were permanently orphaned — recallSkillMemoryBlock returns "" when
frontmatter is disabled, while the agent saw a convincing 'Skill note
saved' response. Now returns an actionable error before any insert.

Red-checked: new regression test fails without the guard (orphan row
inserted + 'saved' response), passes with it (no row, 'not enabled').
iceteaSA pushed a commit to iceteaSA/magic-context that referenced this pull request Jul 2, 2026
…d in frontmatter

Counterpart to ctx_skill_recall's enabled-guard (greptile review, PR cortexkit#181):
without it, notes for skills that never opted in inserted successfully but
were permanently orphaned — recallSkillMemoryBlock returns "" when
frontmatter is disabled, while the agent saw a convincing 'Skill note
saved' response. Now returns an actionable error before any insert.

Red-checked: new regression test fails without the guard (orphan row
inserted + 'saved' response), passes with it (no row, 'not enabled').
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant